Closes:

Summary

This PR reduces the context window usage when fetching pull request review comments using the pull_request_read tool (get_review_comments).

It does so by using the minimal types pattern (which is already used elsewhere in the codebase for the same reason) to reduce the payload that is sent back to the model when the tool is used. Specifically, GraphQL node IDs are removed, nested author objects are flattened to plain strings, and the Comments.Nodes nesting is flattened to a direct comments array, eliminating unnecessary JSON noise per review thread.

Tests & Metrics

When tested with this PR:
Before: 6815 tokens
After: 5823 tokens
Context reduction: 14.56%

Fields preserved

Thread: is_resolved, is_outdated, is_collapsed, comments, total_count
Comment: body, path, line, author (flattened from Author.Login), created_at, updated_at, html_url (from URL)
Pagination: has_next_page, has_previous_page, start_cursor, end_cursor, total_count

Fields dropped

Thread ID (GraphQL node ID, not used for pagination or any subsequent tool call), Comment ID (GraphQL node ID, not useful for reasoning — html_url is the meaningful identifier)

Why

The raw GraphQL response returned by the GitHub API includes GraphQL node IDs on both threads and comments, deeply nested author objects (Author.Login), and a nested Comments.Nodes array structure that add up across threads and waste context window on every call. These fields are not used by models for reasoning or follow-up tool calls — pagination relies on cursors, and the html_url serves as the useful comment identifier.

What changed

• Added MinimalPageInfo, MinimalReviewComment, MinimalReviewThread, and MinimalReviewThreadsResponse types to minimal_types.go
• Added convertToMinimalReviewThreadsResponse, convertToMinimalReviewThread, and convertToMinimalReviewComment converter functions
• Updated GetPullRequestReviewComments to return via MarshalledTextResult instead of manual json.Marshal of raw GraphQL structs
• Updated tests to assert against typed MinimalReviewThreadsResponse fields instead of map[string]any

MCP impact

• No tool or API changes
• Tool schema or behavior changed
• New tool added

Security / limits

• No security or limits impact
• Auth / permissions considered
• Data exposure, filtering, or token/size limits considered

Tool renaming

• I am renaming tools as part of this PR (e.g. a part of a consolidation effort)
  • I have added the new tool aliases in deprecated_tool_aliases.go
• I am not renaming tools as part of this PR

Note: if you're renaming tools, you must add the tool aliases. For more information on how to do so, please refer to the official docs.

Lint & tests

• Linted locally with ./script/lint
• Tested locally with ./script/test

Docs

• Not needed
• Updated (README / docs / examples)